Systems and methods for detecting, reporting and cleaning metadata from inbound attachments

ABSTRACT

Systems and methods consistent with various disclosed embodiments provide for detecting, reporting, removing and cleaning metadata from inbound email attachments. In one embodiment, a system is disclosed that may be associated with a client device operated by an electronic message recipient. The system may include a memory storing instructions and one or more processors configured to execute the instructions to perform one or more operations. The operations may include intercepting an inbound electronic message sent to the recipient and determining that an electronic document attached to the inbound electronic message includes metadata. The operations may also include creating a modified electronic document by removing at least a portion of the metadata from the attached electronic document, generating a report describing metadata included in the attached electronic document, and generating information for sending the report and the inbound electronic message with the modified electronic document to the client device.

FIELD

The present disclosure generally relates to systems and methods for managing and cleaning attachments. In particular, the disclosed embodiments generally relate to systems and methods for managing and cleaning inbound electronic message attachments.

BACKGROUND

Electronic messages, such as email, have become a prevalent means of sending and receiving information. Such information may be contained in an email message itself, as well as in an electronic document or file included as an attachment to such an electronic message. Senders of email messages often include electronic documents and files attached to email messages, and electronic documents and files attached to email messages often include metadata such as Macros and/or VBA code which can be used to hide, install, and run harmful scripts on a computer when the recipient opens the attachments. Such metadata in email attachments may pose certain security risks and concerns to recipients of email.

One conventional means of screening inbound emails with attached electronic documents has included the use of spam or junk email filters. The use of spam filters, however, often results in recipients failing to review emails and electronic documents due to their spam categorization and relegation to a spam or junk folder. In addition, while various antivirus software products such as Norton Antivirus™, McAfee™ AntiVirus Plus, Barracuda Web Filter, and Stanford Anti-Malware provide a certain level of protection to email recipients, such products do not provide for the removal of metadata including VBA code which is not considered malware by itself but can be used to camouflage and hide malware in electronic documents attached to inbound emails. There is also the need to inspect the attachments to detect the metadata and to provide the recipient with a report on the metadata found in the inbound attachments.

Thus, current products do not provide enough versatility and convenience for efficiently detecting, reporting, removing and cleaning metadata from inbound email attachments. For example, conventional systems do not analyze incoming emails for attachments containing metadata and clean such metadata from attachments before the incoming emails arrive at an email exchange server or arrive at a user's email inbox. Conventional systems also do not generate reports to recipients on detected or removed metadata from inbound email attachments. Nor do such systems allow for an interface that permits users to set email attachment metadata cleaning options for inbound emails, including designating predetermined types of metadata for removal or reporting and designating processes for the review of inbound email attachments.

Accordingly, there is a need for systems and methods that provide greater versatility and convenience for detecting, reporting, removing and cleaning metadata from inbound email attachments.

SUMMARY

The disclosed embodiments provide, among other things, systems and methods for detecting, reporting, removing and cleaning inbound email attachments.

In one embodiment, a system is disclosed for cleaning metadata from inbound attachments. The system may be associated with a client device operated by an electronic message recipient. The system may include a memory storing instructions and one or more processors configured to execute the instructions to perform one or more operations. The one or more operations may include intercepting an inbound electronic message sent to the recipient. The one or more operations may also include determining that an electronic document attached to the inbound electronic message includes metadata. The one or more operations may also include creating a modified electronic document by removing at least a portion of the metadata from the attached electronic document. The one or more operations may further include generating a report describing metadata included in the attached electronic document. In addition, the one or more operations may include generating information for sending the report and the inbound electronic message with the modified electronic document to the client device.

In another embodiment, a method is disclosed for cleaning metadata from inbound attachments. The method may include intercepting, at an intermediate computer that is associated with a client device operated by an electronic message recipient, an inbound electronic message sent to the recipient. The method may include may also include determining that an electronic document attached to the inbound electronic message includes metadata. The method may also include may also include creating a modified electronic document by removing at least a portion of the metadata from the attached electronic document. The method may further include generating a report describing metadata included in the attached electronic document. In addition, the method may include generating information for sending the report and the inbound electronic message with the modified electronic document to the client device.

In another embodiment, a non-transitory computer-readable storage medium is disclosed. The storage medium may store instructions for cleaning metadata from inbound attachments. The instructions may cause one or more computer processors to perform one or more operations. The one or more operations may include intercepting, at an intermediate computer that is associated with a client device operated by an electronic message recipient, an inbound electronic message sent to the recipient. The one or more operations may also include determining that an electronic document attached to the inbound electronic message includes metadata. The one or more operations may also include creating a modified electronic document by removing at least a portion of the metadata from the attached electronic document. The one or more operations may further include generating a report describing metadata included in the attached electronic document. In addition, the one or more operations may include generating information for sending the report and the inbound electronic message with the modified electronic document to the client device.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only. Exemplary objects and advantages of the disclosed embodiments are set forth below, and in part will be apparent from the description, or may be learned by practice of the disclosed embodiments. Certain objects and advantages of the disclosed embodiments may be realized and attained by means of the elements and combinations particularly pointed out in the appended claims.

BRIEF DESCRIPTION OF DRAWING(S)

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate various embodiments and aspects of the disclosed embodiments. In the drawings:

FIG. 1A illustrates an exemplary system environment consistent with disclosed embodiments;

FIG. 1B is a diagram illustrating an exemplary inbound metadata system consistent with disclosed embodiments;

FIG. 2 is a diagram illustrating an exemplary electronic message reflecting certain aspects consistent with disclosed embodiments;

FIG. 3 is a flowchart illustrating an exemplary inbound email attachment process consistent with disclosed embodiments;

FIG. 4 is a flowchart illustrating an exemplary inbound email attachment process consistent with disclosed embodiments; and

FIG. 5 is a diagram illustrating an exemplary interface reflecting certain aspects consistent with disclosed embodiments.

DETAILED DESCRIPTION

Reference will now be made in detail to exemplary disclosed embodiments, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.

FIG. 1A illustrates an exemplary system environment 100 consistent with certain disclosed embodiments. System 100 may include one or more clients 102, 104 that may be connected to a network 120 and can communicate with each either via electronic messages (e.g., email) sent over network 120 (e.g., the Internet). For example, client 104 may be configured to send emails containing one or more attachments over network 120, and client 102 may be configured to receive emails containing one or more attachments over network 120. In certain embodiments, system 100 may enable client 102 to receive emails sent by client 104 containing one or more attachments via an email system 110 and/or an inbound metadata system 112. In still other embodiments, client 104 may be configured to receive emails containing one or more attachments over network 120, and client 102 may be configured to send such emails to client 104 via an email system and an inbound metadata system.

Client 102, 104 may be a computer system including one more computing components for performing one or more processes consistent with certain aspects of the disclosed embodiments. In one embodiment, client 102, 104 may include one or more computer or data processing devices such as a PC, laptop computer, desktop computer, tablet, mobile phone, smart phone, or other mobile devices that have hardware (e.g., one or more processors, storage memory, data buses, network interface, etc.), software (e.g., web browsers, application programs, operating systems, add-ins for software programs or systems, other executable program code written in any known programming language such as PUSQL, AJAX, XML, JavaScript™, C, C++, Java™, etc.), and/or firmware (e.g., software embedded in a hardware device). Client 102, 104 may be configured to communicate with one or more networks, such as network 120, and with other clients or servers connected to network 120, including other computers or components connected to a local network. Client 102, 104 may execute software processes stored on tangible and non-transitory computer-readable mediums that perform one or more processes consistent with the disclosed embodiments.

One or more users may operate one or more components of client 102, 104 to perform one or more processes consistent with the disclosed embodiments. Client 102, 104 may be associated with an entity, such as a company, organization, government agency, educational or medical facility, firm, or any other type of business or non-business entity. In certain embodiments, client 102 may be associated with an entity that is different from that associated with client 104. Alternatively, client 102 and client 104 may be associated with the same entity. Further, client 102 may be associated with a department, division, etc., of an entity that is different from a department, division, etc., of the same entity associated with client 104.

While FIG. 1A illustrates two clients 102, 104, aspects of the disclosed embodiments are not limited to such a configuration. Thus, the disclosed embodiments may be implemented with any number of clients interconnected by one or more networks, including but not limited to network 120. Further, the term “client” used herein to describe client 102, 104 is not intended to be limiting to a client in the sense of known client-server configurations, although such configurations may be implemented by the disclosed embodiments. For example, client 102, 104, may be (or include) a server-type computer system or server software that may also request and receive information, data, services, processes, etc., from another computer system in a local and/or remote network.

In one embodiment, client 102, 104 may employ hardware, software, or firmware to create, save, send, receive, delete, and the like, one or more electronic messages, such as email messages. In one embodiment, client 104 and its respective user(s) or entity(ies) associated with client 104 may be a sender of an email. For example, a client 104 may be operated by a sender to create, maintain, save, store, or otherwise prepare an email. A client 104 may additionally be operated by a sender to attach one or more attachments to an email. Client 102 may be operated or configured by a recipient to receive an email from a sender operating client 104. In certain aspects, a recipient operating client 102 may receive an email that may contain or more attachments from a sender operating client 104. In other embodiments, client 102 may similarly be operated to perform the same or similar operations as client 104, and vice versa. Other clients (not shown) may also be implemented such that each may be senders, recipients, or both, respective to other clients.

Network 120 may be any type of communication network configured to communicate information in system 100. Network 120 may be a wireless and/or wireline network including one or more components (e.g., hardware, software, and/or firmware) configured to receive, route, translate, and deliver information. For example, network 120 may be the Internet, an Extranet, an Intranet, a Local Area Network, Wide Area Network, etc., and combinations of such exemplary networks, that enables clients (or other computer systems) to communicate in accordance with aspects of the disclosed embodiments. Network 120 may include infrastructure that implements the communication of information over these types of networks, such as routers, bridges, servers, wireless/wireline base stations, transceivers, and related technology. In certain embodiments, network 120 may be separate networks that connect client 102 and client 104 either directly or indirectly. In other embodiments, network 120 may connect client 102, 104 to an email system 110 or an inbound metadata system 112, or to other intermediate servers, computer systems, or other devices. In still other embodiments, network 120 may connect client 102 and client 104 through separate networks or connections within the same network via an email system 110 or an inbound metadata system 112, or to other intermediate servers, computer systems, or other devices. For example, network 120 may include a local area network, wide area network, portions of the Internet etc., that provide connections between client 102 and client 104 that is different (in whole or in part) than a local area network, wide area network, portions of the Internet etc., that provides connections between client 102, 104 and different intermediate servers, computer systems, or other devices.

Email system 110 may be a system that provides email functions, applications, and other types of services consistent with the disclosed embodiments, e.g., such as an email exchange server. In certain embodiments, email system 110 may be a web-based email system that interconnects with one or more clients, such as clients 102, 104, over the Internet. Consistent with the disclosed embodiments, email system 110 may include one or more servers and memory storage devices that host or provide email applications and/or services. Email system 110 may include one or more computer or data processing devices that have hardware, software, and/or firmware. Email system 110 may also include one or more memory devices, such as local or networked memory storage media, shared memory platforms, or a combination thereof. In certain embodiments, email system 110 includes memory that stores emails, folders of emails, documents, email attachments, information, data, etc., for sending, receiving, and viewing by clients 102, 104 through a browser or similar type of software application. In certain embodiments, email system 110 may be incorporated into a client 102, 104, and in other embodiments it may be separate from client 102, 104, and connected to client 102, 104 via a network, such as network 120. In certain aspects, email system 110 may be a system that provides other functionalities in addition to the email functionalities disclosed herein.

Email system 110 may be configured to execute software that performs processes consistent with the disclosed embodiments. For example, email system 110 may perform one or more processes that intercept, receive, and/or control access to emails, attachments, documents, folders of documents, or any other content associated with emails. Email system 110 may also perform processes that enable clients 102, 104 (or their users) to send, receive, save, store, archive, and the like, emails, attachments, documents, folders of documents, or other content over network 120. In certain disclosed embodiments, email system 110 may also provide attachment management operations, such as PDF conversion, binding, reordering of attachments, renaming of attachments, division of attachments into one or more additional attachments, division of attachments into one or more additional emails, Bates-numbering, cover-page insertion, separator sheet insertion, creating access rights, content viewing, editing, collaboration, redacting, approving, comparing, cleaning metadata, reporting, and/or administrative applications, calendar, and security functions.

Inbound metadata system 112 may be a system that provides metadata cleaning services, as well as email functions, applications, and other types of services consistent with the disclosed embodiments. In certain disclosed embodiments, inbound metadata system 112 may be a computer system connected to client 102, email system 110, and/or client 104 over network 120. In one example, inbound metadata system 112 may include one or more computer or data processing devices that have hardware, software, and/or firmware. Inbound metadata system 112 may also include one or more memory devices, such as local or networked memory storage media, shared memory platforms, or a combination thereof. In certain embodiments, inbound metadata system 112 may be incorporated into a client 102, 104 and/or email system 110, and in other embodiments it may be separate from client 102, 104 and/or email system 110 and connected to client 102, 104 and/or email system 110 via a network, such as network 120.

FIG. 1B is a block diagram illustrating an exemplary inbound metadata system 112 consistent with the disclosed embodiments. Inbound metadata system 112 may include a metadata detection module 114, which may forensically analyze email attachments to determine their file types, and to detect and identify the types of metadata (e.g., descriptive, structural, administrative, macros, VBA code, etc.) contained in attachments. Consistent with the disclosed embodiments, an administrator of inbound metadata system 112 or client 102 may configure metadata detection module 114 to detect metadata based on a list of predetermined types of metadata, or based on categories of metadata as described herein. Inbound metadata system 112 may also include a metadata cleaning module 116, which may remove a portion of detected metadata in an attachment, or remove the entirety of the detected metadata in an attachment. For example, an administrator of inbound metadata system 112 or client 102 may configure metadata cleaning module 116 to clean certain predetermined types of metadata, or to remove all detected metadata from attachments. Inbound metadata system 112 may additionally include a metadata reporting module 118, which may generate reports for sending to, e.g., client 102, describing the types of metadata detected in email attachments, providing options for analyzing and/or cleaning metadata detected in email attachments, or describing types of metadata cleaned from email attachments. Metadata reporting module 118 may also generate alerts to, e.g., client 102, when metadata is detected, analyzed, and/or cleaned in an email attachment. Inbound metadata system 112 may further include a data storage 120, where inbound metadata system 112 may store and/or queue intercepted emails and attachments for metadata detection, analysis, reporting, and/or removal, and to quarantine emails and/or attachments that contain metadata that cannot be removed.

Inbound metadata system 112 may be configured to execute software that performs processes consistent with the disclosed embodiments. For example, inbound metadata system 112 may intercept and/or control access to electronic messages (e.g., emails), attachments, documents folders of documents, or any other content associated with emails. Inbound metadata system 112 may also perform processes to analyze emails, attachments, documents, folders of documents, or any other content associated with emails for metadata and to detect, prepare & send reports to recipient, clean and remove such metadata. In certain embodiments, inbound metadata system 112 may be configured to intercept inbound emails sent to client 102 and analyze and clean metadata from attachments to such inbound emails. In certain disclosed embodiments, inbound metadata system 112 may be configured (e.g., by an email recipient operating client 102 and/or an email sender operating client 104) to clean predetermined types of metadata from attachments. Inbound metadata system 112 may also be configured to determine the file type of an attachment to an email and the origin of the email, such as the sender's email address or IP address. Consistent with the disclosed embodiments, inbound metadata system 112 may be a system that provides other functionalities in addition to the metadata cleaning and other email functionalities expressly described herein.

Returning to FIG. 1A, consistent with the disclosed embodiments, email system 110 and/or inbound metadata system 112 may be associated with an email recipient operating client 102. For example, email system 110 may comprise an email exchange server that provides email services to a client 102 within a local or wide area network. In certain embodiments, email system 110 may reside within or on a firewall of an organization, company, or other entity including a client 102 receiving an inbound email. Similarly, inbound metadata system 112 may be associated with an email recipient operating client 102 and may also reside within or on a firewall of an organization, company, or other entity that includes client 102. In certain embodiments, inbound metadata system 112 may be implemented as a system within email system 110. In other embodiments, inbound metadata system 112 may be an intermediate computer system between client 102 and email system 110, and in still other embodiments, inbound metadata system 112 may reside outside of both client 102 and email system 110, on the one hand, and inside of client 104, on the other hand. When an email sender operating client 104 sends an email over network 120 to a recipient operating client 102, email system 110 and/or inbound metadata system 112 associated with client 102 may intercept the email and perform operations consistent with the disclosed embodiments on the email and any email attachments before permitting the email to continue to client 102. In certain disclosed embodiments, inbound metadata system 112 may analyze the email for attachments, determine the file type of attachments, analyze attachments for metadata, clean metadata from attachments, prepare and send reports regarding metadata in attachments, generate alerts regarding metadata in attachments, quarantine emails and/or attachments, and permit emails and attachments to proceed to email system 110 and/or client 102. In other embodiments, inbound metadata system 112 may receive or intercept an email from email system 110 and perform similar operations on the email and/or attachment before permitting it to proceed to client 102.

FIG. 2 is a diagram illustrating an exemplary electronic message 201 consistent with the disclosed embodiments. In certain embodiments, email 201 may contain an attachment 202. An attachment 202 may be selected from any type of file, such as a document, a spreadsheet, a text file, an image, a database, a temporary buffer, a web-page, an email, a worksheet, a .PDF, .DOC, .EXE, .PPTX or .XLS file, or any other type of file or structure used to store information. An attachment 202 may also be a folder or sub-folder containing one or more files, or a combination of one or more files, including but not limited to bound files, merged files (e.g., PDFs), .ZIP and other types of files. An attachment may be a file created, reviewed, revised, edited, or otherwise modified by a user operating an application or other software at client 102, 104. In certain aspects, an attachment 202 may also have certain access or security rights associated with it (e.g., read-only, edit-only, comment-only, confidential, highly confidential, etc.). The above-listed examples of attachments are not intended to be limiting of the scope of the disclosed embodiments.

Consistent with the disclosed embodiments, an attachment 202 may contain primary data 203 and metadata 204. For example, primary data 203 may comprise the information content of attachment 202, including text, objects, figures, images, formatting data, font data, page-break data, paragraph separation and format, text size and type, and the like. Metadata 204 may include, for example, information that is not primary data 203 or information not immediately apparent to a user operating client 102, 104 in an attachment 202. Consistent with certain embodiments, metadata 204 may include information that describes attributes of an attachment. For example, descriptive metadata may include data concerning the author or creator of an attachment 202, the original file name of the attachment 202, the time and date that attachment 202 was created and/or modified, indications that the content of attachment 202 has been modified (e.g., comments and redline edits), and version or editing history information for attachment 202, including user identifications, edits, and editing times. Metadata may also include structural metadata relating to the components of an attachment and relationships between them. Metadata may further include administrative metadata relating to, e.g., collaboration attributes or access rights for reviewing an attachment or performing operations on an attachment (e.g., reviewing, edits, approving, comparing, transmitting, etc.). Metadata may also include other information contained within an attachment 202, such as macros, VBA variables, and/or other executable code within an electronic document. As used herein with respect to the disclosed embodiments, the term “metadata” does not include viruses, although certain disclosed embodiments may provide for the analysis and removal of both metadata and viruses.

In certain embodiments, email 201 may be an email sent from the address of a user operating client 104 to the address of a recipient operating client 102. In other embodiments, email 201 may similarly be sent by a user operating client 102 and received at a recipient operating client 104. Email 201 may also intercepted by email system 110 and/or inbound metadata system 112 before it is received at client 102, 104. Upon intercepting an email 201, email system 110 and/or inbound metadata system 112 may perform operations on the email 201 and/or attachment 202 consistent with the disclosed embodiments. Once email system 110 and/or inbound metadata system 112 performs operations on an email 201 and/or attachment 202, email system 110 and/or inbound metadata system 112 may send, forward, or otherwise permit email 201 to proceed to a recipient operating, e.g., client 102.

FIG. 3 is a flowchart illustrating an exemplary inbound metadata detection, cleaning, and reporting cleaning process 300 consistent with certain disclosed embodiments. Each step of process 300 may be performed by one or more of client 102, by email system 110, and/or by inbound metadata system 112. While process 300 is described herein with respect to certain embodiments, process 300 is not limited to such a configuration of components of system 100 and to such a distribution of operations, as different combinations of components and operations may similarly be used to perform the steps of process 300.

In certain disclosed embodiments, an inbound metadata system 112 associated with client 102 may intercept an inbound email 201 designating client 102 as a recipient (step 302). For example, email 201 may designate client 104 as the sender, and inbound metadata system 112 may receive inbound email 201 over network 120 before it arrives to either client 102 or email system 110. In other embodiments, email system 110 may receive email 201 over network 120 from client 104, and may permit it to proceed to inbound metadata system 112.

In step 304, inbound metadata system 112 may analyze any attachments 202 to email 201 for metadata. In certain embodiments, inbound metadata system 112 associated with client 102 may analyze an attachment 202 for predetermined types of metadata 204 according to a metadata cleaning policy designated by client 102. In other embodiments, inbound metadata system 112 may be configured to detect specific types of metadata. If, at step 304, inbound metadata system 112 detects no metadata associated with an attachment 202 to email 201, it may allow the email 201 and attachment to be sent onwards to client 102 and/or email system 110 in step 320.

If, however, inbound metadata system 112 detects metadata associated with an attachment 202 to email 201, inbound metadata system 112 may generate a report describing, e.g., the detected metadata, the file type of the attachment, and options for analyzing or cleaning the metadata (step 306). At step 308, inbound metadata system 112 may send the report to a recipient operating client 102 or to a designated administrator of system 112.

At step 310, inbound metadata system 112 may determine whether the metadata needs to be cleaned or removed. In one embodiment, inbound metadata system 112 may perform operations to remove or retain metadata in response to instructions received from client 102 or an administrator after analyzing the report sent in step 308. In certain disclosed embodiments, inbound metadata system 112 associated with client 102 may determine whether metadata associated with an attachment 202 matches a predetermined type of metadata for cleaning or removal according to a metadata cleaning policy designated by client 102 or an administrator. In other embodiments, inbound metadata system 112 may be configured to determine whether specific types or prevalence of metadata needs to be removed. If inbound metadata system 112 determines that metadata does not need to be removed, it may allow the email 201 and attachment to be sent onwards to client 102 and/or email system 110 in step 320.

If inbound metadata system 112 determines that metadata needs to be removed, process 300 may proceed to step 312. At step 312, inbound metadata system 112 may clean or remove metadata from the attachment 202 to email 201. At step 314, inbound metadata system 112 may allow sending of email 201 with the cleaned attachment towards client 102 either directly or indirectly (e.g., via email system 110).

FIG. 4 is a flowchart illustrating another exemplary metadata detection, cleaning, and reporting process 400 consistent with certain disclosed embodiments. Each step of process 400 may be performed by one or more of client 102, by email system 110, and/or by inbound metadata system 112. While process 400 is described herein with respect to certain embodiments, process 400 is not limited to such a configuration of components of system 100 or to such a distribution of operations, as different combinations of components and operations may be used to perform the steps of process 400.

In one embodiment, inbound metadata system 112 associated with client 102 may receive an inbound electronic message 201 (e.g., email) designating client 102 as recipient (step 402). In certain embodiments, a user operating client 104 may be a sender of email 201, and inbound metadata system 112 may receive inbound email 201 over network 120 before it arrives to either client 102 or email system 110. In other embodiments, email system 110 may receive email 201 over network 120 from client 104, and may permit it to proceed and be received or intercepted by inbound metadata system 112. In still other embodiments, email system 110 may receive an email 201, send it to inbound metadata system 112 to perform one or more steps of process 400, after which metadata system 112 may return the email 201 to email system 110 to send to client 102, to perform other steps of process 400, or to perform yet other operations on email 201 and/or its attachments. Inbound metadata system 112 and/or email system 110 may intercept an inbound electronic message 201 by, e.g., recognizing the domain or IP address associated with the designated recipient of the inbound electronic message 201 and temporarily retaining the message 201 to perform one or more steps of process 400.

In step 404, inbound metadata system 112 may determine the origin of the email 201. Consistent with the disclosed embodiments, if inbound metadata system 112 determines that email 201 originated from an authorized sender (e.g., client 104), inbound metadata system 112 may allow email 201 and any attachments to be sent onwards to client 102 and/or email system 110 without further analysis or operations (step 430). If inbound metadata system 112 determines that email 201 did not originate from an authorized sender, it may proceed to perform one or more steps of process 400. In certain disclosed embodiments, inbound metadata system 112 may evaluate, e.g., the email address, IP address, or other credentials associated with the sender of email 201 to determine the origin of email 201 and whether email 201 originated from an authorized sender. Authorized senders may include, e.g., users operating clients (e.g., client 104) within a company, organization, or other entity, or users otherwise designated by client 102 and/or an administrator. Consistent with certain disclosed embodiments, client 102 and/or an administrator may configure inbound metadata system 112 to recognize certain email senders as authorized or unauthorized senders through the use of email exchange accounts, a white list, registration in a directory, and the like.

In step 406, inbound metadata system 112 may determine whether email 201 contains an attachment 202. If email 201 does not contain an attachment, inbound metadata system 112 may allow email 201 to be sent to client 102 and/or email system 110 (step 430). If inbound metadata system 112 determines that email 201 contains an attachment 202, inbound metadata system 112 may recognize or determine the file type of the attachment (step 408). In one embodiment, inbound metadata system 112 may be configured to perform operations to determine the file type of the attachment regardless of the attachment's designated file extension. For example, inbound metadata system 112 may analyze the underlying code of an attachment 202 to determine that an attached document may be an MS Word or Excel file despite having a .PDF extension. In other embodiments, inbound metadata system 112 may determine that an attachment with a .DOC extension is in fact a PDF file. Inbound metadata system 112 may perform still other operations to determine the true file type of an attachment, regardless of whether such attachment has been renamed to provide the appearance of being another file type (e.g., to circumvent security measures).

In certain embodiments, upon determining the file type of an attachment, inbound metadata system 112 may allow the email to be sent to client 102 and/or email system 110 (step 430). In certain disclosed embodiments, inbound metadata system 112 may be configured (e.g., by client 102 or an administrator of a network, organization, or application, etc.) to allow emails having certain predetermined types of documents attached to proceed without further analysis or operations. In other embodiments, if inbound metadata system 112 cannot determine the file type of an attachment 202, inbound metadata system 112 may quarantine the email 201 and/or attachment in step 440.

In step 440, consistent with certain disclosed embodiments, inbound metadata system 112 may store the email 201 and/or attachment 202 for quarantine. In other examples, inbound metadata system 112 may forward email 201 and/or attachment 202 to email system 110 and/or client 102 for quarantine storage. Consistent with the disclosed embodiments, inbound metadata system 112 may enable various operations for the review of emails and/or attachments in quarantine. As one example, inbound metadata system 112 may provide quarantined emails and/or attachments to client 102 or a designated administrator for further review and analysis. In other examples, inbound metadata system 112 may provide for client 102 or a designated administrator to select settings for receiving and reviewing quarantined emails and/or attachments. In still other examples, inbound metadata system 112 may generate a log of quarantined emails and/or attachments and provide the log to client 102 or a designated administrator for review, which may further include options for enabling review and analysis of such quarantined emails and/or attachments. In certain embodiments, inbound metadata system 112 may only quarantine a subset of the attachments to an email 201 and allow the remainder to be sent to client 102 or to proceed through the remaining steps of process 400. In other embodiments, metadata system 112 may quarantine all attachments if one attachment to an email 201 is quarantined, and in other embodiments, inbound metadata system 112 may quarantine both the email 201 and all of its attachments.

If inbound metadata system 112 determines the file type of an attachment 202 to email 201 in step 408, inbound metadata system 112 may proceed to determine whether the attachment 202 contains metadata (step 410). In certain embodiments, inbound metadata system 112 may determine that an attachment to email 201 does not contain any metadata and allow the email 201 and attachment to be sent to client 102 and/or email system 110 (step 430). In other embodiments, inbound metadata system 112 may determine that an attachment contains metadata 204, and proceed to determine whether the metadata 204 needs to be cleaned or removed (step 412). In certain embodiments, inbound metadata system 112 may determine that the metadata matches a predetermined type of metadata (e.g., as configured by client 102 and/or an administrator). In other embodiments, inbound metadata system 112 may be configured to determine whether specific types of metadata need to be removed or that a certain prevalence of metadata exists (e.g., a ratio of metadata to primary data) and needs to be removed.

If inbound metadata system 112 determines that the metadata does not need to be cleaned, it may allow the email 201 and its attachment to be sent to client 102 and/or email system 110 (step 430) without further operations or analysis. In other embodiments, inbound metadata system 112 may determine that the metadata needs to be cleaned and proceed determine whether the metadata can be cleaned from the attachment (step 414). If inbound metadata system 112 determines that it cannot clean the metadata from the attachment, process 400 may proceed to step 440 and inbound metadata system 112 may quarantine the email and/or attachment. If inbound metadata system 112 determines that it can clean all or a portion of the metadata, it may automatically clean the metadata (or at least a portion of the metadata) from the attachment (step 416). In step 416, in certain embodiments, inbound metadata system 112 may remove the metadata from the attachment to email 201. In other embodiments, inbound metadata system 112 may also generate a cleansed version of an attachment to email 201 and replace the original attachment to email 201 with the cleansed version.

In step 418, inbound metadata system 112 may generate a report that may describe, e.g., the file type of attachment 202, the types of metadata detected in attachment 202, the metadata cleaned from attachment 202, the metadata remaining in attachment 202, and/or whether any quarantine of the email 201 or attachment 202 may be necessary. In other embodiments, inbound metadata system 112 may generate a report that also provides options to a recipient operating client 102 or to an administrator regarding, e.g., whether certain types of metadata should be removed from an attachment 202, or whether portions or all of an attachment should be quarantined.

At step 420, inbound metadata system 112 may proceed to allow sending of the email 201 and cleaned attachment to client 102 and/or email system 110. In certain embodiments, inbound metadata system 112 may analyze the email 201 to determine the next hop (e.g., by IP address or domain) and accordingly send the email 201 onwards to the next hop, e.g., to email server 110 or client 102. In step 422, inbound metadata system 112 may also send the report generated in step 418 to either client 102 or an administrator. In certain embodiments, inbound metadata system may generate and send a unique report for each email 201 and/or attachment 202. In other disclosed embodiments, inbound metadata system may generate a log accessible by client 102 or an administrator with entries corresponding to particular emails 201 and attachments 202. For example, rather than creating and sending a unique report, inbound metadata system may populate an entry in the log for an attachment 202 containing similar information as a unique report would, and generate a notification to a recipient operating client 102 and/or an administrator that the log has been updated.

Variations on process 400 and rearrangements and reordering of one or more steps may occur without departing from the spirit of the disclosed embodiments. For example, among other possible reorderings of steps, process 400 may begin at step 404 instead of step 402, and vice versa. Non-dependent steps may be performed in any order, or in parallel. In other examples, process 400 may generate and send a report (steps 418 and 422) before cleaning metadata (step 416), or before allowing sending of a cleaned attachment (step 420). In other disclosed embodiments, process 400 may omit certain steps or include additional steps as may be apparent from the embodiments disclosed herein.

One or more components of system 100 may perform additional operations specific to one or more aspects of the disclosed embodiments. For example, FIG. 5 is a diagram illustrating an exemplary interface 500 consistent with the disclosed embodiments. One or more components of system 100 may provide for an interface 500 for a user operating client 102 to configure inbound metadata system 112 to perform certain functionalities, which may be related to one more steps of processes 300 or 400. The one more components of system 100 may provide interface 500 within a standalone program or application, or as a menu or table associated with an application or email platform (e.g., MS Outlook, Gmail, Hotmail, etc.)

Consistent with the disclosed embodiments, interface 500 may provide a menu, table, or listing of selectable options 502 for a user operating client 102 to configure inbound metadata system 112 to recognize certain authorized senders or domains of senders according to designated email addresses, IP addresses, or other security criteria (e.g., authentication keys, logins and passwords, etc.) In other embodiments, interface 500 may provide a menu, table, or listing of selectable options 504 for a user operating client 102 to determine particular types of metadata (e.g., VBA variables, editing identifiers, version history, etc.) to detect, analyze, report, and/or clean.

Interface 500 may additionally provide a menu, table, or listing of selectable options 506 for a user operating client 102 to provide for the generation of reports and the review of quarantined emails and/or attachments. In certain examples, a user operating client 102 may configure inbound metadata system 112 to generate a report or update an existing report to describe, e.g., the metadata detected and/or cleaned from an attachment 202. In certain examples, a user operating client 102 may also configure inbound metadata system 112 to generate a log of quarantined emails and attachments along with their detectable attributes (e.g., file type, sender address or identity, metadata, etc.) and provide the log to client 102 and/or a designated administrator for review. In other examples, a user operating client 102 may configure inbound metadata system 112 to enable the review of quarantined emails and/or attachments at client 102 within a protected mode, such as opening the emails and attachments while deactivating any executable code within such attachments, or by opening the emails and attachments within a virtual memory at inbound metadata system 112 and temporarily rendering them for display to a user operating client 102.

In yet additional embodiments, interface 500 may provide a menu, table, or listing of selectable options 508 for a user operating client 102 to configure inbound metadata system 112 to generate an alert, e.g., if an incoming email contains an attachment that includes metadata or if inbound metadata system 112 cleaned certain metadata in accordance with certain disclosed embodiments. Similarly, inbound metadata system 112 may be configured to generate an alert if an intercepted email contained an attachment that could not be analyzed or cleaned, and to communicate the reason why the attachment could not be analyzed or cleaned (e.g., “This inbound file could not be cleaned of macros.” or “This inbound file type could not be determined.”). In yet other embodiments, interface 500 may provide options for a user operating client 102 to configure inbound metadata system 112 to perform similar metadata cleaning operations on both inbound and outbound emails and attachments.

Other aspects of the disclosed embodiments will be apparent to those skilled in the art from consideration of the specification and practice of the disclosed embodiments disclosed herein. It is intended that the specification and examples be considered as exemplary only, with particular examples of the disclosed embodiments being indicated by the following claims. 

What is claimed is:
 1. A computer-based system for cleaning metadata from inbound attachments, comprising: an intermediate computer that is associated with a client device operated by an electronic message recipient, the intermediate computer comprising: a memory storing instructions; and one or more processors configured to execute the instructions to: intercept an inbound electronic message sent to the recipient, determine that an electronic document attached to the inbound electronic message includes metadata, create a modified electronic document by removing at least a portion of the metadata from the attached electronic document, generate a report describing metadata included in the attached electronic document, and generate information for sending the report and the inbound electronic message with the modified electronic document to the client device.
 2. The system of claim 1, wherein the one or more processors are further configured to execute the instructions to; determine that at least a portion of the metadata from the attached electronic document cannot be removed, and send the attached electronic document to a quarantine storage.
 3. The system of claim 2, wherein the one or ore processors are further configured to execute the instructions to: generate an entry in a log including an identification of the attached electronic document and an indication that at least a portion of the metadata from the attached electronic document could not be removed; and provide the log to the client device.
 4. The system of claim 1, wherein the one or more processors are further configured to execute the instructions to intercept the inbound electronic message from an intermediate email server associated with the client device.
 5. The system of claim 1, wherein the one or more processors are further configured to execute the instructions to send the inbound electronic message with the modified electronic document to an intermediate email server associated with the client device.
 6. The system of claim 1, wherein the removed portion of the metadata includes descriptive metadata or administrative metadata.
 7. The system of claim 1, wherein the descriptive metadata includes author data, editing history, or an indication of modified content in the attached electronic document.
 8. A computer-based method for cleaning metadata from inbound attachments, comprising: intercepting, at an intermediate computer that is associated with a client device operated by an electronic message recipient, an inbound electronic message sent to the recipient, determining that an electronic document attached to the inbound electronic message includes metadata, creating a modified electronic document by removing at least a portion of the metadata from the attached electronic document, generating a report describing metadata included in the attached electronic document, and generating information for sending the report and the electronic inbound message with the modified electronic document to the client device.
 9. The method of claim 8, further comprising: determining that at least a portion of the metadata from the attached electronic document cannot be removed, and sending the attached electronic document to a quarantine storage.
 10. The method of claim 9, further comprising: generating an entry in a log including an identification of the attached electronic document and an indication that at least a portion of the metadata from the attached electronic document could not be removed; and providing the log to the client device.
 11. The method of claim 8, further comprising intercepting the inbound electronic message from an intermediate email server associated with the client device.
 12. The method of claim 8, further comprising sending the inbound electronic message with the modified electronic document to an intermediate email server associated with the client device.
 13. The method of claim 8, wherein the removed portion of the metadata includes descriptive metadata or administrative metadata.
 14. The method of claim 8, wherein the descriptive metadata includes author data, editing history, or an indication of modified content in the attached electronic document.
 15. A non-transitory computer-readable storage medium storing instructions for cleaning metadata from inbound attachments, the instructions causing one or more computer processors to perform operations comprising: intercepting, at an intermediate computer that is associated with a client device operated by an electronic message recipient, an inbound electronic message sent to the recipient, determining that an electronic document attached to the inbound electronic message includes metadata, creating a modified electronic document by removing at least a portion of the metadata from the attached electronic document, generating a report describing metadata included in the attached electronic document, and generating information for sending the report and the electronic inbound message with the modified electronic document to the client device.
 16. The storage medium of claim 15, wherein the instructions cause the one or more processors to further perform the operations of: determining that at least a portion of the metadata from the attached electronic document cannot be removed, and sending the attached electronic document to a quarantine storage.
 17. The storage medium of claim 16, wherein the instructions cause the one or more processors to further perform the operations of: generating an entry in a log including an identification of the attached electronic document and an indication that at least a portion of the metadata from the attached electronic document could not be removed; and providing the log to the client device.
 18. The storage medium of claim 15, wherein the instructions cause the one or more processors to further perform the operations of intercepting the inbound electronic message from an intermediate email server associated with the client device.
 19. The storage medium of claim 15, wherein the instructions cause the one or more processors to further perform the operations of sending the inbound electronic message with the modified electronic document to an intermediate email server associated with the client device.
 20. The storage medium of claim 15, wherein the removed portion of the metadata includes descriptive metadata comprising author data, editing history, or an indication of modified content in the attached electronic document. 